Subject: Capabilites - include also configuration ?

From: [email-masked] (azi)
Date: Wed, 14 Jul 93 08:24:04 +0200

Hi,

One of the problems mentioned by many vendor regarding the DLSw protocol
is the large amount of configuration that has to be done for a single 
DLSw node, mainly the need the specify all other DLSw in the network.

Is the capabilities SIGlet/protocol may be the one to overcome this problem ?

When capabilities are exchanged, a list of already known DLSw nodes can
be sent. As a result, one (or more) DLSw nodes can serve as 'name servers'
While other nodes can connect those and receive an update list DLSw nodes.
The name server may have a preconfigure list of nodes, and it can also
collect them dynamically, when other nodes establish connection.

Elazar (Azi) Ronen, RADLINX

---

From: [email-masked]
Date: Wed, 14 Jul 93 00:12:07 PDT

>Is the capabilities SIGlet/protocol may be the one to overcome this problem ?

    I would think the Capabilities SIGlet is the place to work on
    it.  In my opinion, capabilitites exchanges occur before any
    circuit connection traffic.

>collect them dynamically, when other nodes establish connection.

    I like it.  Having a list of DLSw-capable routers in the capabilities
    exchange would tend to direct the format toward a more complex structure.

    The only thing that a heuristic approach like this might impact is the
    ability to build segmented domains of DLSw-capable routers.  With
    manual definition of participating routers, the network administrator
    can point them wherever he/she chooses.

    Comments from others?

>Elazar (Azi) Ronen, RADLINX

Wayne